Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding docker upgrade rollout strategy #7315

Merged

Conversation

raymond-zhang00
Copy link
Contributor

Issue #, if available:
#6719

Description of changes:
Adding UpgradeRolloutStrategy knobs for workers and control plane to docker provider

Testing (if applicable):
Updated unit tests.

Documentation added/planned (if applicable):
Planning on adding docs on knobs for other providers following the Tinkerbell upgrade strategy format.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@eks-distro-bot eks-distro-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 17, 2024
Copy link

codecov bot commented Jan 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ca3bcd4) 71.72% compared to head (78895d7) 71.72%.
Report is 9 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7315   +/-   ##
=======================================
  Coverage   71.72%   71.72%           
=======================================
  Files         559      559           
  Lines       43368    43377    +9     
=======================================
+ Hits        31104    31113    +9     
  Misses      10549    10549           
  Partials     1715     1715           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@g-gaston g-gaston left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@@ -327,6 +327,38 @@ func TestProviderGenerateDeploymentFileSuccessUpdateMachineTemplate(t *testing.T
wantCPFile: "testdata/valid_deployment_cp_expected.yaml",
wantMDFile: "testdata/valid_autoscaler_deployment_md_expected.yaml",
},
{
testName: "valid config with rollout",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll leave it up to you but I would prefer if we tested these things through ControlPlaneSpec and WorkersSpec

That decouples the tests from the fact that these spec builders return yaml (which they should never have)

I understand you are just following whatever was in here, which is fair. But It would be better if we could start writing new tests following a better pattern.

This applies to all providers

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense, swapping over to ControlPlaneSpec and WorkersSpec tests instead for all providers

@eks-distro-bot eks-distro-bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed lgtm size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 18, 2024
@raymond-zhang00 raymond-zhang00 force-pushed the add-docker-upgrade-rollout-strategy branch from b79b377 to 78895d7 Compare January 18, 2024 20:14
Copy link
Member

@g-gaston g-gaston left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@raymond-zhang00
Copy link
Contributor Author

/approve

@eks-distro-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: raymond-zhang00

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@eks-distro-bot eks-distro-bot merged commit 66db899 into aws:main Jan 19, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants